home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Freeware 1998 June
/
SGI Freeware 1998 June.iso
/
dist
/
fw_unzip.idb
/
usr
/
freeware
/
catman
/
u_man
/
cat1
/
zipinfo.Z
/
zipinfo
Wrap
Text File
|
1998-05-21
|
27KB
|
595 lines
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
NNNNAAAAMMMMEEEE
zipinfo - list detailed information about a ZIP archive
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
zzzziiiippppiiiinnnnffffoooo [----11112222ssssmmmmllllvvvvhhhhMMMMttttTTTTzzzz] _f_i_l_e[._z_i_p] [_f_i_l_e(_s) ...]
[----xxxx _x_f_i_l_e(_s) ...]
uuuunnnnzzzziiiipppp ----ZZZZ [----11112222ssssmmmmllllvvvvhhhhMMMMttttTTTTzzzz] _f_i_l_e[._z_i_p] [_f_i_l_e(_s) ...]
[----xxxx _x_f_i_l_e(_s) ...]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_z_i_p_i_n_f_o lists technical information about files in a ZIP
archive, most commonly found on MS-DOS systems. Such
information includes file access permissions, encryption
status, type of compression, version and operating system or
file system of compressing program, and the like. The
default behavior (with no options) is to list single-line
entries for each file in the archive, with header and
trailer lines providing summary information for the entire
archive. The format is a cross between Unix ``ls -l'' and
``unzip -v'' output. See DDDDEEEETTTTAAAAIIIILLLLEEEEDDDD DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN below. Note
that _z_i_p_i_n_f_o is the same program as _u_n_z_i_p (under Unix, a
link to it); on some systems, however, _z_i_p_i_n_f_o support may
have been omitted when _u_n_z_i_p was compiled.
AAAARRRRGGGGUUUUMMMMEEEENNNNTTTTSSSS
_f_i_l_e[._z_i_p]
Path of the ZIP archive(s). If the file specification
is a wildcard, each matching file is processed in an
order determined by the operating system (or file
system). Only the filename can be a wildcard; the path
itself cannot. Wildcard expressions are similar to
Unix _e_g_r_e_p(1) (regular) expressions and may contain:
* matches a sequence of 0 or more characters
? matches exactly 1 character
[...]
matches any single character found inside the
brackets; ranges are specified by a beginning
character, a hyphen, and an ending character. If
an exclamation point or a caret (`!' or `^')
follows the left bracket, then the range of
characters within the brackets is complemented
(that is, anything _e_x_c_e_p_t the characters inside
the brackets is considered a match).
(Be sure to quote any character that might otherwise be
interpreted or modified by the operating system,
particularly under Unix and VMS.) If no matches are
found, the specification is assumed to be a literal
Page 1 (printed 5/6/98)
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
filename; and if that also fails, the suffix .zip is
appended. Note that self-extracting ZIP files are
supported; just specify the .exe suffix (if any)
explicitly.
[_f_i_l_e(_s)]
An optional list of archive members to be processed.
Regular expressions (wildcards) may be used to match
multiple members; see above. Again, be sure to quote
expressions that would otherwise be expanded or
modified by the operating system.
[----xxxx _x_f_i_l_e(_s)]
An optional list of archive members to be excluded from
processing.
OOOOPPPPTTTTIIIIOOOONNNNSSSS
----1111 list filenames only, one per line. This option
excludes all others; headers, trailers and zipfile
comments are never printed. It is intended for use in
Unix shell scripts.
----2222 list filenames only, one per line, but allow headers
(----hhhh), trailers (----tttt) and zipfile comments (----zzzz), as well.
This option may be useful in cases where the stored
filenames are particularly long.
----ssss list zipfile info in short Unix ``ls -l'' format. This
is the default behavior; see below.
----mmmm list zipfile info in medium Unix ``ls -l'' format.
Identical to the ----ssss output, except that the compression
factor, expressed as a percentage, is also listed.
----llll list zipfile info in long Unix ``ls -l'' format. As
with ----mmmm except that the compressed size (in bytes) is
printed instead of the compression ratio.
----vvvv list zipfile information in verbose, multi-page format.
----hhhh list header line. The archive name, actual size (in
bytes) and total number of files is printed.
----MMMM pipe all output through an internal pager similar to
the Unix _m_o_r_e(1) command. At the end of a screenful of
output, _z_i_p_i_n_f_o pauses with a ``--More--'' prompt; the
next screenful may be viewed by pressing the Enter
(Return) key or the space bar. _z_i_p_i_n_f_o can be
terminated by pressing the ``q'' key and, on some
systems, the Enter/Return key. Unlike Unix _m_o_r_e(1),
there is no forward-searching or editing capability.
Also, _z_i_p_i_n_f_o doesn't notice if long lines wrap at the
Page 2 (printed 5/6/98)
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
edge of the screen, effectively resulting in the
printing of two or more lines and the likelihood that
some text will scroll off the top of the screen before
being viewed. On some systems the number of available
lines on the screen is not detected, in which case
_z_i_p_i_n_f_o assumes the height is 24 lines.
----tttt list totals for files listed or for all files. The
number of files listed, their uncompressed and
compressed total sizes, and their overall compression
factor is printed; or, if only the totals line is being
printed, the values for the entire archive are given.
Note that the total compressed (data) size will never
match the actual zipfile size, since the latter
includes all of the internal zipfile headers in
addition to the compressed data.
----TTTT print the file dates and times in a sortable decimal
format (yymmdd.hhmmss). The default date format is a
more standard, human-readable version with abbreviated
month names (see examples below).
----zzzz include the archive comment (if any) in the listing.
DDDDEEEETTTTAAAAIIIILLLLEEEEDDDD DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_z_i_p_i_n_f_o has a number of modes, and its behavior can be
rather difficult to fathom if one isn't familiar with Unix
_l_s(1) (or even if one is). The default behavior is to list
files in the following format:
-rw-rws--- 1.9 unx 2802 t- defX 11-Aug-91 13:48 perms.2660
The last three fields are the modification date and time of
the file, and its name. The case of the filename is
respected; thus files that come from MS-DOS PKZIP are always
capitalized. If the file was zipped with a stored directory
name, that is also displayed as part of the filename.
The second and third fields indicate that the file was
zipped under Unix with version 1.9 of _z_i_p. Since it comes
from Unix, the file permissions at the beginning of the line
are printed in Unix format. The uncompressed file-size
(2802 in this example) is the fourth field.
The fifth field consists of two characters, either of which
may take on several values. The first character may be
either `t' or `b', indicating that _z_i_p believes the file to
be text or binary, respectively; but if the file is
encrypted, _z_i_p_i_n_f_o notes this fact by capitalizing the
character (`T' or `B'). The second character may also take
on four values, depending on whether there is an extended
local header and/or an ``extra field'' associated with the
Page 3 (printed 5/6/98)
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
file (fully explained in PKWare's APPNOTE.TXT, but basically
analogous to pragmas in ANSI C--i.e., they provide a
standard way to include non-standard information in the
archive). If neither exists, the character will be a hyphen
(`-'); if there is an extended local header but no extra
field, `l'; if the reverse, `x'; and if both exist, `X'.
Thus the file in this example is (probably) a text file, is
not encrypted, and has neither an extra field nor an
extended local header associated with it. The example
below, on the other hand, is an encrypted binary file with
an extra field:
RWD,R,R 0.9 vms 168 Bx shrk 9-Aug-91 19:15 perms.0644
Extra fields are used for various purposes (see discussion
of the ----vvvv option below) including the storage of VMS file
attributes, which is presumably the case here. Note that
the file attributes are listed in VMS format. Some other
possibilities for the host operating system (which is
actually a misnomer--host file system is more correct)
include OS/2 or NT with High Performance File System (HPFS),
MS-DOS, OS/2 or NT with File Allocation Table (FAT) file
system, and Macintosh. These are denoted as follows:
-rw-a-- 1.0 hpf 5358 Tl i4:3 4-Dec-91 11:33 longfilename.hpfs
-r--ahs 1.1 fat 4096 b- i4:2 14-Jul-91 12:58 EA DATA. SF
--w------- 1.0 mac 17357 bx i8:2 4-May-92 04:02 unzip.macr
File attributes in the first two cases are indicated in a
Unix-like format, where the seven subfields indicate whether
the file: (1) is a directory, (2) is readable (always
true), (3) is writable, (4) is executable (guessed on the
basis of the extension--._e_x_e, ._c_o_m, ._b_a_t, ._c_m_d and ._b_t_m
files are assumed to be so), (5) has its archive bit set,
(6) is hidden, and (7) is a system file. Interpretation of
Macintosh file attributes is unreliable because some
Macintosh archivers don't store any attributes in the
archive.
Finally, the sixth field indicates the compression method
and possible sub-method used. There are six methods known
at present: storing (no compression), reducing, shrinking,
imploding, tokenizing (never publicly released), and
deflating. In addition, there are four levels of reducing
(1 through 4); four types of imploding (4K or 8K sliding
dictionary, and 2 or 3 Shannon-Fano trees); and four levels
of deflating (superfast, fast, normal, maximum compression).
_z_i_p_i_n_f_o represents these methods and their sub-methods as
follows: _s_t_o_r; _r_e:_1, _r_e:_2, etc.; _s_h_r_k; _i_4:_2, _i_8:_3, etc.;
_t_o_k_n; and _d_e_f_S, _d_e_f_F, _d_e_f_N, and _d_e_f_X.
The medium and long listings are almost identical to the
Page 4 (printed 5/6/98)
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
short format except that they add information on the file's
compression. The medium format lists the file's compression
factor as a percentage indicating the amount of space that
has been ``removed'':
-rw-rws--- 1.5 unx 2802 t- 81% defX 11-Aug-91 13:48 perms.2660
In this example, the file has been compressed by more than a
factor of five; the compressed data are only 19% of the
original size. The long format gives the compressed file's
size in bytes, instead:
-rw-rws--- 1.5 unx 2802 t- 538 defX 11-Aug-91 13:48 perms.2660
Adding the ----TTTT option changes the file date and time to
decimal format:
-rw-rws--- 1.5 unx 2802 t- 538 defX 910811.134804 perms.2660
Note that because of limitations in the MS-DOS format used
to store file times, the seconds field is always rounded to
the nearest even second. For Unix files this is expected to
change in the next major releases of _z_i_p(1L) and _u_n_z_i_p.
In addition to individual file information, a default
zipfile listing also includes header and trailer lines:
Archive: OS2.zip 5453 bytes 5 files
,,rw, 1.0 hpf 730 b- i4:3 26-Jun-92 23:40 Contents
,,rw, 1.0 hpf 3710 b- i4:3 26-Jun-92 23:33 makefile.os2
,,rw, 1.0 hpf 8753 b- i8:3 26-Jun-92 15:29 os2unzip.c
,,rw, 1.0 hpf 98 b- stor 21-Aug-91 15:34 unzip.def
,,rw, 1.0 hpf 95 b- stor 21-Aug-91 17:51 zipinfo.def
5 files, 13386 bytes uncompressed, 4951 bytes compressed: 63.0%
The header line gives the name of the archive, its total
size, and the total number of files; the trailer gives the
number of files listed, their total uncompressed size, and
their total compressed size (not including any of _z_i_p's
internal overhead). If, however, one or more _f_i_l_e(_s) are
provided, the header and trailer lines are not listed. This
behavior is also similar to that of Unix's ``ls -l''; it may
be overridden by specifying the ----hhhh and ----tttt options
explicitly. In such a case the listing format must also be
specified explicitly, since ----hhhh or ----tttt (or both) in the
absence of other options implies that ONLY the header or
trailer line (or both) is listed. See the EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS section
below for a semi-intelligible translation of this nonsense.
The verbose listing is mostly self-explanatory. It also
lists file comments and the zipfile comment, if any, and the
type and number of bytes in any stored extra fields.
Page 5 (printed 5/6/98)
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
Currently known types of extra fields include PKWARE's
authentication (``AV'') info; OS/2 extended attributes; VMS
filesystem info, both PKWARE and Info-ZIP versions;
Macintosh resource forks; Acorn/Archimedes SparkFS info; and
so on. (Note that in the case of OS/2 extended attributes-
-perhaps the most common use of zipfile extra fields--the
size of the stored EAs as reported by _z_i_p_i_n_f_o may not match
the number given by OS/2's _d_i_r command: OS/2 always reports
the number of bytes required in 16-bit format, whereas
_z_i_p_i_n_f_o always reports the 32-bit storage.)
EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT OOOOPPPPTTTTIIIIOOOONNNNSSSS
Modifying _z_i_p_i_n_f_o's default behavior via options placed in
an environment variable can be a bit complicated to explain,
due to _z_i_p_i_n_f_o's attempts to handle various defaults in an
intuitive, yet Unix-like, manner. (Try not to laugh.)
Nevertheless, there is some underlying logic. In brief,
there are three ``priority levels'' of options: the default
options; environment options, which can override or add to
the defaults; and explicit options given by the user, which
can override or add to either of the above.
The default listing format, as noted above, corresponds
roughly to the "zipinfo -hst" command (except when
individual zipfile members are specified). A user who
prefers the long-listing format (----llll) can make use of the
_z_i_p_i_n_f_o's environment variable to change this default:
ZIPINFO=-l; export ZIPINFO Unix Bourne shell
setenv ZIPINFO -l Unix C shell
set ZIPINFO=-l OS/2 or MS-DOS
define ZIPINFO_OPTS "-l" VMS (quotes for _l_o_w_e_r_c_a_s_e)
If, in addition, the user dislikes the trailer line,
_z_i_p_i_n_f_o's concept of ``negative options'' may be used to
override the default inclusion of the line. This is
accomplished by preceding the undesired option with one or
more minuses: e.g., ``-l-t'' or ``--tl'', in this example.
The first hyphen is the regular switch character, but the
one before the `t' is a minus sign. The dual use of hyphens
may seem a little awkward, but it's reasonably intuitive
nonetheless: simply ignore the first hyphen and go from
there. It is also consistent with the behavior of the Unix
command _n_i_c_e(1).
As suggested above, the default variable names are
ZIPINFO_OPTS for VMS (where the symbol used to install
_z_i_p_i_n_f_o as a foreign command would otherwise be confused
with the environment variable), and ZIPINFO for all other
operating systems. For compatibility with _z_i_p(1L),
ZIPINFOOPT is also accepted (don't ask). If both ZIPINFO
and ZIPINFOOPT are defined, however, ZIPINFO takes
Page 6 (printed 5/6/98)
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
precedence. _u_n_z_i_p's diagnostic option (----vvvv with no zipfile
name) can be used to check the values of all four possible
_u_n_z_i_p and _z_i_p_i_n_f_o environment variables.
EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
To get a basic, short-format listing of the complete
contents of a ZIP archive _s_t_o_r_a_g_e._z_i_p, with both header and
totals lines, use only the archive name as an argument to
zipinfo:
zipinfo storage
To produce a basic, long-format listing (not verbose),
including header and totals lines, use ----llll:
zipinfo -l storage
To list the complete contents of the archive without header
and totals lines, either negate the ----hhhh and ----tttt options or
else specify the contents explicitly:
zipinfo --h-t storage
zipinfo storage \*
(where the backslash is required only if the shell would
otherwise expand the `*' wildcard, as in Unix when globbing
is turned on--double quotes around the asterisk would have
worked as well). To turn off the totals line by default,
use the environment variable (C shell is assumed here):
setenv ZIPINFO --t
zipinfo storage
To get the full, short-format listing of the first example
again, given that the environment variable is set as in the
previous example, it is necessary to specify the ----ssss option
explicitly, since the ----tttt option by itself implies that ONLY
the footer line is to be printed:
setenv ZIPINFO --t
zipinfo -t storage [only totals line]
zipinfo -st storage [full listing]
The ----ssss option, like ----mmmm and ----llll, includes headers and footers
by default, unless otherwise specified. Since the
environment variable specified no footers and that has a
higher precedence than the default behavior of ----ssss, an
explicit ----tttt option was necessary to produce the full
listing. Nothing was indicated about the header, however,
so the ----ssss option was sufficient. Note that both the ----hhhh and
----tttt options, when used by themselves or with each other,
override any default listing of member files; only the
Page 7 (printed 5/6/98)
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
header and/or footer are printed. This behavior is useful
when _z_i_p_i_n_f_o is used with a wildcard zipfile specification;
the contents of all zipfiles are then summarized with a
single command.
To list information on a single file within the archive, in
medium format, specify the filename explicitly:
zipinfo -m storage unshrink.c
The specification of any member file, as in this example,
will override the default header and totals lines; only the
single line of information about the requested file will be
printed. This is intuitively what one would expect when
requesting information about a single file. For multiple
files, it is often useful to know the total compressed and
uncompressed size; in such cases ----tttt may be specified
explicitly:
zipinfo -mt storage "*.[ch]" Mak\*
To get maximal information about the ZIP archive, use the
verbose option. It is usually wise to pipe the output into
a filter such as Unix _m_o_r_e(1) if the operating system allows
it:
zipinfo -v storage | more
Finally, to see the most recently modified files in the
archive, use the ----TTTT option in conjunction with an external
sorting utility such as Unix _s_o_r_t(1) (and _t_a_i_l(1) as well,
in this example):
zipinfo -T storage | sort -n +6 | tail -15
The ----nnnn option to _s_o_r_t(1) tells it to sort numerically rather
than in ASCII order, and the ++++6666 option tells it to sort on
the sixth field after the first one (i.e., the seventh
field). This assumes the default short-listing format; if
----mmmm or ----llll is used, the proper _s_o_r_t(1) option would be ++++7777.
The _t_a_i_l(1) command filters out all but the last 15 lines of
the listing. Future releases of _z_i_p_i_n_f_o may incorporate
date/time and filename sorting as built-in options.
TTTTIIIIPPPPSSSS
The author finds it convenient to define an alias _i_i for
_z_i_p_i_n_f_o on systems that allow aliases (or, on other systems,
copy/rename the executable, create a link or create a
command file with the name _i_i). The _i_i usage parallels the
common _l_l alias for long listings in Unix, and the
similarity between the outputs of the two commands was
intentional.
Page 8 (printed 5/6/98)
ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL)))) IIIInnnnffffoooo----ZZZZIIIIPPPP ((((3333 NNNNoooovvvveeeemmmmbbbbeeeerrrr 1111999999997777 ((((vvvv2222....22222222)))))))) ZZZZIIIIPPPPIIIINNNNFFFFOOOO((((1111LLLL))))
BBBBUUUUGGGGSSSS
As with _u_n_z_i_p, _z_i_p_i_n_f_o's ----MMMM (``more'') option is overly
simplistic in its handling of screen output; as noted above,
it fails to detect the wrapping of long lines and may
thereby cause lines at the top of the screen to be scrolled
off before being read. _z_i_p_i_n_f_o should detect and treat each
occurrence of line-wrap as one additional line printed.
This requires knowledge of the screen's width as well as its
height. In addition, _z_i_p_i_n_f_o should detect the true screen
geometry on all systems.
_z_i_p_i_n_f_o's listing-format behavior is unnecessarily complex
and should be simplified. (This is not to say that it will
be.)
SSSSEEEEEEEE AAAALLLLSSSSOOOO
_l_s(1), _f_u_n_z_i_p(1L), _u_n_z_i_p(1L), _u_n_z_i_p_s_f_x(1L), _z_i_p(1L),
_z_i_p_c_l_o_a_k(1L), _z_i_p_n_o_t_e(1L), _z_i_p_s_p_l_i_t(1L)
UUUURRRRLLLL
The Info-ZIP home page is currently at
http://www.cdrom.com/pub/infozip/ .
AAAAUUUUTTTTHHHHOOOORRRR
Greg ``Cave Newt'' Roelofs. ZipInfo contains pattern-
matching code by Mark Adler and fixes/improvements by many
others. Please refer to the CONTRIBS file in the UnZip
source distribution for a more complete list.
Page 9 (printed 5/6/98)